Enabling tracepoints in dpdk-test causes app to exit immediately without running any tests
https://bugs.dpdk.org/show_bug.cgi?id=1715
Bug ID: 1715
Summary: Enabling tracepoints in dpdk-test causes app to exit
immediately without running any tests
Product: DPDK
Version: 25.03
Hardware: POWER
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
While attempting to create a custom tracepoint I discovered that enabling any tracepoints in the dpdk-test app cause if to exit (exit code 255) without running any tests. Here's an example on a ppc64le system:
Quoted 10 lines
$ ~/src/dpdk/build/app/test/dpdk-test -l 2-127 --no-pci --no-huge --trace=lib.mempool.create EAL: Detected CPU lcores: 128 EAL: Detected NUMA nodes: 2 EAL: Static memory layout is selected, amount of reserved memory can be adjusted with -m or --socket-mem EAL: Detected static linkage of DPDK EAL: Multi-process socket /run/user/1000/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: Trace dir: /home/drc/dpdk-traces/rte-2025-05-28-PM-05-10-59
The resulting trace looks like this:
Quoted 29 lines
$ babeltrace2 ~/dpdk-traces/rte-2025-05-28-PM-05-10-59 05-28 17:13:00.352 484540 484540 F LIB/ASSERT-COND bt_lib_assert_cond_failed@lib/assert-cond.c:64 Babeltrace 2 library precondition not satisfied. 05-28 17:13:00.352 484540 484540 F LIB/ASSERT-COND bt_lib_assert_cond_failed@lib/assert-cond.c:65 ------------------------------------------------------------------------ 05-28 17:13:00.352 484540 484540 F LIB/ASSERT-COND bt_lib_assert_cond_failed@lib/assert-cond.c:66 Condition ID: `pre:message-packet-beginning-create-with-default-clock-snapshot:without-default-clock-snapshot`. 05-28 17:13:00.352 484540 484540 F LIB/ASSERT-COND bt_lib_assert_cond_failed@lib/assert-cond.c:68 Function: bt_message_packet_beginning_create_with_default_clock_snapshot(). 05-28 17:13:00.352 484540 484540 F LIB/ASSERT-COND bt_lib_assert_cond_failed@lib/assert-cond.c:69 ------------------------------------------------------------------------ 05-28 17:13:00.352 484540 484540 F LIB/ASSERT-COND bt_lib_assert_cond_failed@lib/assert-cond.c:70 Error is: 05-28 17:13:00.352 484540 484540 F LIB/ASSERT-COND bt_lib_assert_cond_failed@lib/assert-cond.c:72 Unexpected stream class configuration when creating a packet beginning or end message: no default clock snapshot is needed, but one was provided: stream-addr=0x476bcfb0, stream-id=0, stream-name="/home/drc/dpdk-traces/rte-2025-05-28-PM-05-10-59/channel0_0", stream-stream-class-addr=0x47aae210, stream-stream-class-id=0, stream-trace-class-addr=0x47aae0d0, stream-trace-addr=0x474f0800, stream-trace-name="", stream-packet-pool-size=0, stream-packet-pool-cap=0, sc-addr=0x47aae210, sc-id=0, sc-is-frozen=0, sc-event-class-count=532, sc-packet-context-fc-addr=0x47aae5b0, sc-event-common-context-fc-addr=(nil),
Quoted 8 lines
sc-assigns-auto-ec-id=0, sc-assigns-auto-stream-id=0, sc-supports-packets=1, sc-packets-have-begin-default-cs=0, sc-packets-have-end-default-cs=0, sc-supports-discarded-events=0, sc-discarded-events-have-default-cs=0, sc-supports-discarded-packets=0, sc-discarded-packets-have-default-cs=0, sc-trace-class-addr=0x47aae0d0, sc-pcf-pool-size=0, sc-pcf-pool-cap=0, with-cs=1, cs-val=0 05-28 17:13:00.352 484540 484540 F LIB/ASSERT-COND bt_lib_assert_cond_failed@lib/assert-cond.c:75 Aborting...
[1] 484540 abort (core dumped) babeltrace2
~/dpdk-traces/rte-2025-05-28-PM-05-10-59
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.